Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.59%. Comparing base (a944aa5) to head (7f9a2bd).

❗ Current head 7f9a2bd differs from pull request most recent head 4d1e087

Please upload reports for the commit 4d1e087 to get more accurate results.

@@            Coverage Diff             @@
##           master    #3729      +/-   ##
==========================================
+ Coverage   94.47%   97.59%   +3.11%     
==========================================
  Files         134      134              
  Lines        9613     9479     -134     
  Branches     3486     3468      -18     
==========================================
+ Hits         9082     9251     +169     
+ Misses        531      228     -303     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

I see some examples using single and double quotes - great! - but none using backticks. Can we add some? (whether it's supported or not)

I knew I'd miss a few things 😅 Thanks for the feedback, really appreciate it!

Backticks don't work with use server, but great idea to test them. Adding now.

A semi-related question that came to mind that I'd like advice on:

Other ESLint rules like eslint/require-await and typescript-eslint/require-await report async functions that do not have an await operator as incorrect. Any ideas on how we can make rules like these not report on "use server"? Adding options to these rules to ignore functions with certain directives would do the trick, but an option like that is React-specific enough that it's unlikely to get merged.

The require-await rules are harmful and bad and should never have existed in the first place. An async function without any awaits is perfectly acceptable (unlike a generator without a yield).

As such, the solution there is to just disable those horrifically foolish rules.

Rebased. I'd love to see lots more test cases, and I'm not going to merge this until the feature is available in a non-canary full release, so I'll mark it as a draft until then.

Makes sense to me! When the full release rolls around we can spruce up the test cases and get this merged :)

Hi! React 19 launched as stable today.

Are we still interested in getting this merged? If so we can fix merge conflicts and spruce up tests to do so!

@jorgezreik yep, let's do those things :-) mark it as ready for review when you think it's so